-
Notifications
You must be signed in to change notification settings - Fork 807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix four small papercuts #2149
Fix four small papercuts #2149
Conversation
The existing test does not correctly test the "only existing" behavior (and only functions because of a typo in the test), fix that by moving it to before the fallback test (where it needs to be) and correctly setting up the existing names map Also, added some comments to make what is being tested more clear Signed-off-by: Connor Catlett <[email protected]>
Signed-off-by: Connor Catlett <[email protected]>
Signed-off-by: Connor Catlett <[email protected]>
Signed-off-by: Connor Catlett <[email protected]>
Code Coverage DiffThis PR does not change the code coverage |
/retest |
/lgtm |
@ElijahQuinones: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Is this a bug fix or adding new feature?
Bug fix, mostly
What is this PR about? / Why do we need it?
Fixes four small papercuts:
Cleanup TestNameAllocatorLikelyBadName to prevent code coverage flapping
This should prevent code coverage constantly flapping on this test by properly setting up the
existingNames
map. Also, added some comments to make the test more clear.Adjust TestExpiringCache timeouts to decrease CI flakes
This test flakes all the time in CI, especially on the Windows unit tests. I bumped up the sleeps to hopefully combat this, it's set to run in parallel so shouldn't make a significant difference to overall test time.
Standardize deployment methods by removing Kustomize-specific changes
Our helm chart contains two places that are used to magically inject comments into the Kustomize deployment. Remove these to standardize the chart and because they're bad:
In
controller.yaml
, the Kustomize deployment comments out the mode by default, thus running the driver inAll
mode and running the node server on the controller. This is pointless, wastes RAM and CPU, and increases the attack surface.In
serviceaccount-csi-controller.yaml
, the Kustomize deployment has a comment about IRSA. Documenting via comments in the manifests is a horrible practice, EKS Pod Identity is superior to and largely replaces IRSA, and the EKS docs already appropriately document how to use IRSA.Set PATH for kubetest2 so it can find helpers
kubetest2
isn't properly pinned unless its path points to where the helper binaries are installed, as it shells out to the helpers directly. Without this fixkubetest2
must be installed locally and the E2E tests will use the local version instead of the pinned version for half the functionality.What testing is done?
CI/Manual